[Fix] Review labels disappear after base updates - #1584
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Review statusThis PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging. Current step: Mark the PR ready. Required CI must pass before CodeRabbit starts. Review-state labels are managed by this workflow; do not edit them manually. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
1 participant
What changed
Why this change was made
The all-open-PR reconciliation triggered by the merge of #1577 ran while GitHub was recalculating mergeability. Although CodeRabbit approvals remained attached to the exact PR head commits, the unknown-mergeability branch removed otherwise-valid
awaiting-maintainerlabels, making the queue appear to collapse.Impact
Base-branch pushes no longer temporarily erase review-state labels while GitHub recalculates mergeability. Confirmed conflicts still transition to
has-conflicts, and the hourly/event-driven reconciliation still replaces preserved labels once GitHub returns a definitive state.Follow-up to #1577 and #1509.